" In my experience you could not get a more helpful, and patient, supplier than TK." - I agree
TK is very helpful, he helped me many times, fixed bugs in very short time, add write on disk function, fixed trajectory planner etc...
Support here is great.
--- In
DynoMotion@yahoogroups.com, "fermanz" <ferman@...> wrote:
>
> I have been following this thread and it is clear that one of you does not understand what the other is trying to say.
> Perhaps if you, quelisto, were to post the file, that you are trying to compile, and let Tom show you where it is going wrong that could be a way through this.
> I was very surprised to read the antagonistic outburst aimed at someone you want to help you.
> In my experience you could not get a more
helpful, and patient, supplier than TK.
>
>
> --- In
DynoMotion@yahoogroups.com, "quelisto" <quelisto@> wrote:
> >
> > Stdafx was included in the Kmotion475/KmotionDLL folder. If MS wrote it, great, but apparently someone at Dynomtion decided to include it in the software for some reason. I don't want to know the reason or the authorship, I just want to get your product working please!
> >
> > I just want my code to compile. Several of your code examples call for this (and other) header files that are problematic. I can't get those examples to compile, either.
> >
> > So what gives? Can you please just address the root problem, which is that needed header files are either not present or are buried somewhere. I am not
writing a C++ program, I am not using Visual Studio, I am using YOUR product and it is not working, period, so please help me with that. I'd much rather call you to get an answer, because I am trying to get a project done, and then you wouldn't have had a forum full of my questions either.
> >
> > It's simple: all you have to do is solve my problem, and I go away, okay? I can tell you don't like me, fine, but please just do it, we paid for your product, so please stand by it. Thanks.
> >
> >
> > --- In
DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > stdafx.h is the main Microsoft Visual Studio header file for writing Microsoft Foundation Class (MFC) applications for Windows
> > >
>
> > --- On Wed, 6/22/11, quelisto <quelisto@> wrote:
> > >
> > >
> > > From: quelisto <quelisto@>
> > > Subject: [DynoMotion] Re: Amendment to previous query about header files
> > > To:
DynoMotion@yahoogroups.com> > > Date: Wednesday, June 22, 2011, 11:14 AM
> > >
> > >
> > > Â
> > >
> > >
> > >
> > > No, I'm not trying to write Windows programs for the Kflop board.
> > >
> > > I simply want to compile my code in the "C programs" environment.
> > >
> > > Whenever I try to #include stdafx.h, the compiler fails, telling me it cannot find the various afxxxx.h
files. the same program exists for KmotionDLL.h...the compiler cannot find various header files.
> > >
> > > Again I am NOT trying to take a .cpp file from visual studio and compile it, I am t\just trying to compile stuff written with the C programs window. I am using only functiuons that I've seen you use in example code. This SHOULD be working, but something is amiss here.
> > >
> > > --- In
DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > The C Programs Screen in the KMotion.exe application and the� associated and included TCC67 compiler can only be
used to write C programs that execute in the� DSP Chip on the KFLOP board.� If you wish to write Windows programs that execute on the PC you will need something like Visual Studio to do so.
> > > > Ã�Â
> > > > TK
> > > >
> > > > --- On Wed, 6/22/11, quelisto <quelisto@> wrote:
> > > >
> > > >
> > > > From: quelisto <quelisto@>
> > > > Subject: [DynoMotion] Re: Amendment to previous query about header files
> > > > To:
DynoMotion@yahoogroups.com> > > > Date: Wednesday, June 22, 2011, 10:55 AM
> > > >
> > > >
> > > >
Ã�Â
> > > >
> > > >
> > > >
> > > > No, I'm just using the Kmotion program. We don't have Visual Studio, etc. All development is occuring inside the "C program" application of Kmotion475.
> > > >
> > > > But the issue still remains as to why the compiler can't find the necessary header files...I just don't understand this. Is the compiler assuming that I have an install of Visual Studio to supply the needed stdlib.h and the various afxxxx.h files? I just installed this software yesterday, so unless I'm missing something I would htink all of the necessary header files would be somewhere in the Kmotion directory or subdirectories...but htye are not, as far as I can tell.
> > > >
> > > > --- In
DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > > > >
> > > > > It sounds like you are attempting to run Windows C++ code on the KFLOP board?��� The C Language programs that run in KFLOP are very simple and are limited to the functions��� listed in the single header file KMotionDef.h (actually that includes another small header for a few��� PC-DSP common definitions).
> > > > > Ã�â��Ã�Â
> > > > > TK
> > > > >
> > > > > --- On Wed, 6/22/11, quelisto <quelisto@> wrote:
> > > > >
> > > > >
> > > > >
From: quelisto <quelisto@>
> > > > > Subject: [DynoMotion] Amendment to previous query about header files
> > > > > To:
DynoMotion@yahoogroups.com> > > > > Date: Wednesday, June 22, 2011, 8:20 AM
> > > > >
> > > > >
> > > > > Ã�â��Ã�Â
> > > > >
> > > > >
> > > > >
> > > > > Apparently the problem is manifold:
> > > > >
> > > > > a) You have to specify the path in the #include statement; this is pretty frustrating, the complier should be smart enough to look in all of the KMotion folders, or all the header files should
be in one place!
> > > > >
> > > > > b) The following header files that StdAfx #includes are nowhere to be found:
> > > > >
> > > > > afxwin.h> // MFC core and standard components
> > > > > afxext.h> // MFC extensions
> > > > > afxole.h> // MFC OLE classes
> > > > > afxodlgs.h> // MFC OLE dialog classes
> > > > > afxdisp.h> // MFC OLE automation classes
> > > > > afxpriv.h>
> > > > >
> > > > > I also cannot find stdlib.h, math.h, etc.
> > > > >
> > > > > What is going on?
> > > > >
> > > >
> > >
> >
>
